Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

set-up-tee: Mention logout/login for permissions to take effect #904

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

matevz
Copy link
Member

@matevz matevz commented Aug 22, 2024

Noticed I needed to logout/login to my computer for SGX permissions to take effect.

Copy link

netlify bot commented Aug 22, 2024

Deploy Preview for oasisprotocol-docs ready!

Name Link
🔨 Latest commit 51e096e
🔍 Latest deploy log https://app.netlify.com/sites/oasisprotocol-docs/deploys/66c73fcf5e25460008e0367e
😎 Deploy Preview https://deploy-preview-904--oasisprotocol-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@@ -70,7 +70,11 @@ and the user running Oasis Node is `oasis`, you can do:
sudo adduser oasis sgx
```

Failure to do so may result in permission denied errors during runtime startup.
Then, restart your computer or reload the SGX modules for permissions to take
Copy link
Member

@kostko kostko Aug 22, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm, you shouldn't need to restart your computer. However if you are running your node from an interactive session (e.g. a terminal with your user account), then you need to terminate the session (logout) and login again.

But if you are running your node via something like systemd, nothing like that should be needed.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm, you shouldn't need to restart your computer. However if you are running your node from an interactive session (e.g. a terminal with your user account), then you need to terminate the session (logout) and login again.

Oops, you were right. Closing/Opening the terminal app didn't work, because they're probably forked from the kde session anyway, but logging out of the desktop and back in works. Will fix.

@matevz matevz force-pushed the matevz/docs/sgx-premissions-restart branch from 78107f4 to 51e096e Compare August 22, 2024 13:40
@matevz matevz requested a review from kostko August 22, 2024 13:42
@matevz matevz changed the title set-up-tee: Mention restart for permissions to take effec set-up-tee: Mention logout/login for permissions to take effec Aug 22, 2024
@matevz matevz changed the title set-up-tee: Mention logout/login for permissions to take effec set-up-tee: Mention logout/login for permissions to take effect Aug 22, 2024
@@ -70,7 +70,11 @@ and the user running Oasis Node is `oasis`, you can do:
sudo adduser oasis sgx
```

Failure to do so may result in permission denied errors during runtime startup.
Then, log out from your session (desktop, ssh) and back in for permissions to
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe say something like "If you are planning to run your node from an interactive session, make sure to log out from your ...". Because if you are running via systemd or similar, no such thing is needed as the process manager initializes the session.

@matevz matevz self-assigned this Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants